This is the current state of my attempt to fix #117. It's not fully finished yet, but the majority of the work is done. Therefore, please have a look at this pull request and test it with all the test cases you can imagine. I will update the pull request continually.

Finished Tasks

• Database: new column REMOTE_ID (fixes conflicts between parallel creation of different notes locally and remotely)
• DBStatus: LOCAL_CREATED is not used anymore (distinction if Note is new or edited can be made with checking REMOTE_ID=0; fixes conflicts on synchronization and parallel local edits)
• Note: model is split in to DBNote (representing the local DB entry of a note) and OwnCloudNote (representing the remote note, used by NotesClient).
• ItemAdapter/note item layout: show icon for unsynchronized changes (simplifies debugging, includes all changes done in Show icon if a note is not synchronized (hint to a possible error) #121, closes Show an error message if synchronization fails #119)
• NoteSQLiteOpenHelper: database upgrade (add the new column and adapts the data without flushing the database)
• NoteSQLiteOpenHelper: add more constraints for database updates (fixes lost updates due to parallel changes of notes (from synchronization and user interface))
• NoteSQLiteOpenHelper: updateNoteAndSync(): only make database changes, if the content really changed (fixes don't autosave if the note isn't modified #104, at least the original intention of the author).
• NoteSQLiteOpenHelper: remove recurrent code (improves code quality)
• NoteServerSyncHelper: only update if network is connected (fixes lots of thrown exceptions)
• NoteServerSyncHelper: schedule synchronization requests (if synchronization is active or network not connected; fixes missing push of all outstanding changes)
• NoteServerSyncHelper: restructure the communication between synchronization task and user interface.
• NoteServerSyncHelper: consolidate synchronization AsyncTasks into a single one (improves code quality)
• EditNoteActivity: ensures, that auto-save is not called, if the previous auto-save is still running. In addition, start next auto-save not before a small delay has passed. (This could fix Editing saves on every keypress. It hammers my connection. #76)

Other Issues I've Found (not covered by this pull request)

• There is no conflict resolution for the case that a Note is locally and remotely edited in parallel (e.g. during a longer time without network connection). Currently, local changes overwrite remote changed. We have to discuss what would be the desired behavior. See also Handle remote note deleted #66.
• The ItemAdapter should use a CursorAdapter which is updated automatically if the backend data is changed.
• In order to save traffic during synchronization, pullRemoteChanges() could use the exclude parameter of the Notes API in a first step to check which notes changed without downloading unchanged notes. Only in the second step, the whole note content would be downloaded from the changed note. This could save traffic, however, it has to be investigated if the effort worth it (what is the typical/topmost number and size of notes?).